System and method for using a mark-up language page to command an appliance

ABSTRACT

A hand-held device having a display and a browser application which supports functionality particularly suited for the hand-held device. For example, the browser application supports a full screen tag which allows information to be displayed as a full screen within the display. The browser application may also support a tag for use in displaying a link the activation of which will cause the hand-held device to transmit command codes to a consumer appliance. Still further, the browser application can support a tag which the hand-held device can use to issue reminders.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.11/088,694, filed on Mar. 24, 2005, which application is a continuationof U.S. application Ser. No. 09/905,396, filed on Jul. 13, 2001, whichapplication claims the benefit of U.S. Provisional Patent ApplicationNo. 60/264,767, filed on Jan. 29, 2001, all of which are herebyincorporated by reference in their entirety.

BACKGROUND OF THE INVENTION

This invention relates generally to hand held devices and, moreparticularly, relates to a hand held device having a browserapplication.

Home appliances continue to become more complex, and for many consumers,more difficult to fully understand and operate. The first consumerelectronic devices, radios and, later, televisions, had no remotecontrols. The controls of these first consumer electronic devices weresimple—a combination power switch and volume control and a tuningcontrol. With the advent of the remote control, new capabilities tocontrol were added to consumer electronic devices—one of the first beingthe volume “Mute” feature.

New, and eventually popular, consumer electronic devices were laterintroduced, including the VCR, CD player and more recently, the DVDplayer and PVR (personal video recorder). While the VCR was initiallyintroduced without a remote control, remote controls were quickly addedto the product offering. Early VCR remote controls simply controlled thepower and the transport mechanism (“Play,” “Stop,” “Pause,” “Rewind,”“Fast Forward” and “Record”). Today, VCR remote controls have far morecontrols, for example, to control the adjustment of tape tracking, theselection of programs for future recording, direct channel access,frame-by-frame program viewing and the ability to set the VCR's clock.For use in controlling these features the VCR remote control has grownfrom seven or eight keys to twenty or more.

The CD player, when first introduced, came with a remote control. Thefirst CD players held a single disk and were easy to control. Today, aconsumer can buy a CD player that holds two hundred or more disks. ThisCD “jukebox” permits the consumer to painstakingly enter the title ofeach disk by remote control and control which disk and track of thatdisk will play next. This remote control has also grown from ten keys orso to over thirty with many keys performing two or more functions.

Not only have the consumer electronic devices and their remote controlsbecome more complex, but there are now many more devices that consumersare adding to their home that can be controlled using a remote control.In addition to the TV, VCR, CD player, and DVD player, remote controlscan be used in connection with personal computers, game consoles, etc.Remote controls can also be used to control the lighting, windowfixtures, thermostats, home alarm system, etc. within the home.

Universal remote controls available today perform a valuable function,consolidating three, four, five, and more remote controls into onedevice. Typically, the universal remote control simplifies operation byreducing the number of keys and, therefore, the number of featuresavailable to the consumer. With the same number of keys as found on oneremote control, the universal remote control can operate the basicfunctions of several home appliances.

For companies that provide remote controls, home appliances continuetheir march toward even greater complexity. As new and more complex homeappliances emerge, a new form of easy-to-use remote control will berequired to meet the needs of consumers. To appeal to the largest numberof consumers, this new form of remote control must also be inexpensive.Furthermore, to accommodate the continuing growth in complexity of homeappliances, this new form of remote control must possess new featuresand include the ability to stay flexible.

SUMMARY OF THE INVENTION

In accordance with these needs, the subject invention is directed to ahand-held device having a display and a browser application whichsupports functionality particularly suited for the hand-held device. Forexample, the browser application supports a full screen tag which allowsinformation to be displayed as a full screen within the display. Thebrowser application may also support a tag for use in displaying a linkthe activation of which will cause the hand-held device to transmitcommand codes to a consumer appliance. Still further, the browserapplication can support a tag which the hand-held device can use toissue reminders.

A better understanding of the objects, advantages, features, propertiesand relationships of the invention will be obtained from the followingdetailed description and accompanying drawings which set forth anillustrative embodiment which is indicative of the various ways in whichthe principles of the invention may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention, reference may be had to apreferred embodiment shown in the following drawings in which:

FIG. 1 illustrates a pictorial drawing of a universal remote control inwhich the principles of the subject invention may be embodied;

FIG. 2 illustrates an exploded assembly drawing of the universal remotecontrol illustrated in FIG. 1;

FIG. 3 illustrates a block diagram of exemplary hardware for use inconnection with the universal remote control illustrated in FIG. 1;

FIG. 4 illustrates an exemplary operating system and hardware hierarchyfor use in the universal remote control illustrated in FIG. 1;

FIG. 5 illustrates an exemplary remote control application programhierarchy for use in the universal remote control illustrated in FIG. 1;

FIG. 6 illustrates an exemplary sub-application program hierarchy foruse in setting up the universal remote control illustrated in FIG. 1;

FIG. 7 illustrates an exemplary sub-application program hierarchy foruse in personalizing the universal remote control illustrated in FIG. 1;

FIG. 8 illustrates an exemplary sub-application program hierarchy foruse in establishing the overall system behavior of the universal remotecontrol illustrated in FIG. 1;

FIG. 9 illustrates an exemplary process for initializing a browserapplication resident on the universal remote control illustrated in FIG.1;

FIGS. 10A, 10B, 10C, 10D, 10E, 10F, and 10G illustrate an exemplaryoperational sequence of the browser application resident on theuniversal remote control illustrated in FIG. 1;

FIG. 11 illustrates an exemplary browser screen layout capable of beingdisplayed on the universal remote control of FIG. 1;

FIG. 12 illustrates an exemplary browser-based home control screendisplayed on the universal remote control of FIG. 1 and the HTML sourcefor use in displaying the control screen;

FIG. 13 illustrates an exemplary browser-based TV guide screen displayedon the universal remote control of FIG. 1 and the HTML source for use indisplaying the TV guide screen;

FIG. 14 illustrates a two-way communication system including a computer,a computer network, and the universal remote control illustrated in FIG.1;

FIG. 15 illustrates an exemplary Server Application Flow Chart for usein connection with the two-way communication system illustrated in FIG.14;

FIG. 16 illustrates an exemplary display of Web-based data using thebrowser of the universal remote control illustrated in FIG. 1;

FIG. 17 illustrates the universal remote control illustrated in FIG. 1docked to an optional keyboard;

FIGS. 18A and 18B illustrate an exemplary method by which the remotecontrol illustrated in FIG. 1 can be used to retrieve informationregarding an appliance and the resulting display of an exemplaryretrieved user's manual;

FIGS. 19A and 19B illustrate a further exemplary method by which theremote control illustrated in FIG. 1 can be used to retrieve informationregarding an appliance and the resulting display of an exemplaryretrieved user's manual;

FIG. 20 illustrates an exemplary menu page for use in retrievinginformation regarding an appliance displayed on the remote controlillustrated in FIG. 1;

FIG. 21 illustrates an exemplary error message displayed on the remotecontrol illustrated in FIG. 1 displayed due to an error incommunication;

FIG. 22 illustrates a two-way communication system including anappliance and the universal remote control illustrated in FIG. 1;

FIG. 23 illustrates an alternative two-way communication systemincluding an appliance and the universal remote control illustrated inFIG. 1;

FIG. 24 illustrates an exemplary display of screens used to display songlyrics using the remote control illustrated in FIG. 1;

FIG. 25 illustrates an exemplary system for use in displaying closedcaptioning information using the remote control illustrated in FIG. 1;

FIG. 26 illustrates an exemplary method for use in displaying closedcaptioning information using the system illustrated in FIG. 25.

FIG. 27 illustrates an exemplary display of screens used to display TVguide information and to set and display reminders to watch certainshows using the remote control illustrated in FIG. 1;

FIG. 28 illustrates an exemplary method by which the remote controlillustrated in FIG. 1 can generate reminder displays of the typeillustrated in FIG. 27;

FIG. 29 illustrates an exemplary display of screens used to provideadditional information about a product whose UPC bar code has beenentered using a bar code reader attached to the remote controlillustrated in FIG. 1; and

FIG. 30 illustrates an exemplary display of screens used to display TVguide information ordered according to individual preference.

DETAILED DESCRIPTION

Referring now to FIGS. 1 and 2, there is illustrated a universal remotecontrol device 10, sometimes referred to as the “Mosaic” in the figures,in which the teachings of the present invention may be embodied. Theremote control 10 comprises a housing 11 itself comprising two parts,namely, an upper housing 12 and a lower housing 13. Included in thelower housing 12 is a battery cover 14, a stylus repository, and a slot16 through which a liquid crystal display (LCD) contrast control switch42 may be accessed. Stylus 19 may be located in the stylus repository.

The upper housing 12 has openings through which keys 20, red lightemitting diode (LED) 22 and a LCD 24 with a translucent touch sensitiveoverlay can be accessed. The keys 20 are illustrated as being arrangedin a vertical line to the right of the LCD 24 and may comprise (from topto bottom) a “Backlight” key 30, “Volume Up” and “Volume Down” keys 32and 34, “Mute” key 36, and “Channel Up” and “Channel Down” keys 38 and40, respectively. The contrast control switch 42 can be located on theright side of the remote control 10 below the “Volume Up” and “VolumeDown” keys, 38 and 40. The upper housing 12 may also include an openingfor voice access to a microphone.

At the top or forward end of the remote control 10, there is illustratedan opening for two forward facing infrared LEDs 50 and two side facingLEDs 51. While the LEDs are provided for transmitting command signals toconsumer devices, the forward facing LEDs 50 may also perform as aninfrared light detector according to the teachings of co-pending U.S.patent application Ser. No. 09/080,125 which is incorporated herein byreference in its entirety. The opening in which the LEDs 50 and 51 arecarried may be covered by an infrared-transparent lens 17. The forwardend of the remote control 10 may also include an opening for an RFantenna 52. On the underneath portion of the remote control 10 arelocated openings for a battery compartment 58 and, optionally, aspeaker, and/or battery charging contacts. On the left side of theremote control 10 can be placed a jack 61 reserved for serial dataoperations. In certain embodiments, a magnetic modem coupler 71, asdescribed in U.S. Pat. No. 5,537,463 which is incorporated herein byreference in its entirety, can be included to permit transfer of datainto the unit via a telephone handset or other source of magneticallyencoded signal such as television or P.C. loudspeakers.

Referring now to FIG. 3, there is illustrated a block diagram ofexemplary operating circuitry 100 of the remote control 10. Theoperating circuitry 100 may be powered directly by a battery orindirectly from another electrical source (i.e., by way of the batterycharging contacts or other dc power source). The power supply isregulated and monitored by a power conditioning and status circuit 106.The operating circuitry 100 preferably includes a memory bank 110comprising RAM 111 and flash memory 112, main processor 101 (e.g., aSharp LU77790A), a display module 180 comprising a liquid crystaldisplay glass 182, touch panel overlay 184, electroluminescent backlight186 and drivers 188.

Also included in the operating circuitry 100 are shown a general purposeserial I/O circuit 108, an infrared controller 140 (e.g, comprising aSamsung KS88C01424 Microcontroller), an infrared transmitter circuit150, an infrared receiver circuit 160, a Analog-to-Digital converter(ADC) and touch decoder circuit 170 (e.g., comprising a PIC16LC715Microcontroller or other touch screen controller/decoder chip), aspeaker or buzzer 102, a key pad 190 (the electrical diagram equivalentof the elastomeric keyboard 20 shown in FIG. 2), a magnetic modem 71,and an RF module 152 comprising an RF controller 120 (e.g., a PIC16F84Microcontroller) and an RF transceiver 130 (e.g. an RF MicrodevicesRF2915 chip). In an alternative embodiment, the RF module 125 maycomprise an “off-the-shelf” RF transceiver unit with an integralbaseband processor such as the “900 MHz Microhopper” available fromWorld Wireless Communications Inc. (part number 011-1882). It will beappreciated that RF modules of other manufacture and/or othertechnologies (Bluetooth, IEE802.11, etc.) are equally suitable. The RFcircuitry is connected to the RF antenna 52 while the IR circuitry isconnected to the IR LEDs 50 and 51.

The main processor (e.g., a Sharp “System on a Chip,” the LU77790A) maybe based on a 32-bit, ARM RISC (Reduced Instruction Set Computer) core.In this regard, the main processor would comprise the ARM processor core300, LCD controller 310, general purpose I/O ports 320, and multipleserial UART ports 330. The main processor is provided to manage theentire process of interacting with the user through the backlit,graphical, touchscreen, LCD module 180, the speaker or buzzer 102, thekey pad 190, the microphone and/or the red LED 235 (LED 22 of FIGS. 1and 2) and to provide two-way infrared and RF communications through theinfrared controller 140 and the RF controller 120.

FIG. 3 further illustrates the electrical connections between thevarious modules such as connection 200 interconnecting the memory module110 with the main processor 101, connections 210 and 220 interconnectingthe LCD 180 with the main processor 101, connections 230, 240, 250, 260,and 270 interconnecting the main processor 101 with the key pad 190,buzzer 102, the general purpose serial I/O circuit 108 and the RFcontroller 120, infrared controller 140, and ADC and touch decodercircuit 170, respectively. Other connections include the connection 252between the RF controller 120 and the RF transceiver 130 and connection262 interconnecting the infrared controller 140 with the infraredtransmitter 150 and also connecting the infrared controller 140 with theinfrared receiver 160.

The electronic configuration illustrated in block diagram 100 comprisesa general purpose, multi-processor system. The operation of themulti-processor system is controlled by internal control software. Thecontrol software may include routines, programs, objects, components,and/or data structures that perform particular tasks that can be viewedas an operating system together with one or more applications. Theoperating system provides an underlying set of management and controlfunctions which are utilized by the applications to offer user functionssuch as control of consumer appliances, access to Internet data, displayof home automation controls, display of TV guide information, and thelike. It should be understood that, while the term “remote control” isused herein to designate the physical unit, in terms of the internalsoftware architecture the conventional “clicker” remote control userinterface is but one of several possible applications which may co-existwithin the unit.

Architecturally, the system is organized around the concept of Eventsand Resources. Events are occurrences which initiate an action. Morespecifically, an Event is an occurrence that requires a response fromthe remote control 10. Events include user-initiated activities such aspressing a physical key on the keypad 20, activating the touch screenLCD 24, speaking into a microphone, etc. Events can also be generated bythe main processor 101, for example by an internal timer register. Inaddition, Events can be generated by external means such as, forexample, a communication transmission.

In response to an Event, the remote control will typically access one ormore of its Resources. A Resource is, in its broadest definition, ablock of data. The data is often of a specific (i.e., defined) type.Within the memory 110, each memory data block is preferably identifiedby its “Resource ID” or by another indication where the Resource islocated in the memory structure. Examples of Resources are bitmaps,strings, and control and display definitions. Generally, Resources areused to configure the remote control 10 to be responsive to the needs ofthe user. Many Resources are loaded into the memory 110 of the remotecontrol 10 by the manufacturer when the remote control 10 is built.Other Resources may be created or modified by the user and still otherResources can be remotely loaded into the memory 110 by a servicecenter, via the Internet, etc. Resources allow the behavior, look andfeel of the remote control 10 to be altered, even after it has been soldand is in the hands of the user thus permitting the user to personalizethe remote control 10 to his or her own tastes.

For ease of development, Resources may be instantiated within the remotecontrol 10 by use of a Resource Compiler running on a PC or equivalent.The Resource Compiler accepts a text description of graphic and controlelements and compiles them into memory data structures suitable for usewithin the remote control 10. Although other mechanisms, e.g. manualcompilation, self generation by the remote control operating systemunder user control, etc., are possible, a PC based Resource Compiler mayprovide the most efficient method for rapid development of Resourcesneeded for a particular remote control application. To assist in abetter understanding of the Resources used to construct the remotecontrol user interface software described herein, examples of commandswhich are available in an exemplary Resource Compiler for use ingenerating the memory data structures for the remote control include:

BITMAP (BitMapName, BitsPerPixel, Width, Height, Radix)

The BITMAP command generates a black and white bitmap Resource.“BitMapName” is the bitmap Resource ID while the “Width” and “Height”size the bitmap. “BitsPerPixel” is set to ‘1’ and “Radix” is set to ‘2’in the first generation of the remote control product.

FONT (FontName, StartAsciiIndex, EndAsciiIndex)

FONT generates a Resource Table that associates numeric values withbitmaps. This approach permits the use of an unordered set of bitmaps tobe used as alphabetic characters or font. “FontName” is a SYMBOL. Itsassigned value is the Resoure ID of the font. “StartAsciiIndex” is theindex value associated with the first bitmap ID. “EndAsciiIndex” is theindex value associated with the last bitmap ID. A list of bitmap Idsfollows this Command. The bitmap IDs are typically expressions in theform of SYMBOL names.

STRING (StringName, StringCharacters)

STRING generates a String Resource. “StringName” is a SYMBOL. Itsassigned value is the String Resource ID. “StringCharacters” comprisethe text in the string.

DATA (DataName, [DataSpecifier,[Expr]],DataEnd)

DATA generates a Data Resource. “DataName” is a SYMBOL. Its assignedvalue is the Data Resource ID. “DataSpecifier” indicates the size of theexpressions (“Expr”) that follow it. There can be multiple expressionsfollowing a DataSpecifier and there can be multiple DataSpecifiers in aData Resource.

BITMAPBUTTONCONTROL (ControlName, ControlCode, UpBitMapID, DownBitMapID,InactiveBitMapID, SelectBitMapID)

BITMAPBUTTONCONTROL generates a bitmap push button control.“ControlName” is a SYMBOL. Its assigned value is the Resource ID for thecontrol. “ControlCode” is the value generated when the control on thetouchscreen display is pressed or released. “UpBitMapID” is the ResourceID of the bitmap that is drawn on the display when the control is activebut not pressed. “DownBitMapID” is the Resource ID of the bitmap that isdrawn on the display when the control is active and pressed by the user.“InactiveBitMapID” is the Resource ID of the bitmap that is drawn on thedisplay when the control is inactive. “SelectedBitMapID” is the ResourceID of the bitmap that is drawn on the display when the control is activeand visually highlighted.

STRINGBITMAPCONTROL (ControlName, ControlCode, StringID, FontID,UpBitMapID, DownBitMapID)

STRINGBITMAPCONTROL generates a bitmap push button control on thedisplay with a string drawn over it. “ControlName” is a SYMBOL. Itsassigned value is the Resource ID for the control. “ControlCode” is thevalue generated when the control on the touchscreen is pressed orreleased. “StringID” is the Resource ID of the string that is drawn whenthe control is pressed or unpressed. “FontID” is the Resource ID of thefont with which the string is drawn. “UpBitMapID” is the ResourceID ofthe bitmap that is drawn on the display when the control is active butnot pressed. “DownBitMapID” is the Resource ID of the bitmap that isdrawn on the display when the control is active and pressed by the user.

COMPOSITECONTROL (ControlName, TopX, TopY, ControlCode, Parameters[Below], End)

Rect: Xoffset, Yoffset, Width, Height, ForeGroundColor, BackGroundColor

BitMap: BitMapID, Xoffset, Yoffset, XferMethod

Line: X1offset, Y1offset, X2offset, Y2offset

RoundRect: Xoffset, Yoffset, Width, Height, Radius, ForeGroundColor,BackGroundColor

Text: StringID, Xoffset, Yoffset, Spacing, ForeGroundColor,BackGroundColor, Direction, FontID

ClipRect: Xoffset, Yoffset, Width, Height

COMPOSITECONTROL generates a bitmap control for display from acollection of drawing primitives. The control may be used as a pictureor as a pushbutton control. Unlike other controls just mentioned, thiscontrol does not change when pressed. “ControlName” is a SYMBOL. Itsassigned value is the Resource ID for the control. “TopX” is the leftcoordinate of the control. “TopY” is the top coordinate of the control.“ControlCode” is the value generated when the control on the touchscreendisplay is pressed or released. The parameters are optional graphiccommands. They are:

-   -   ‘Red’ defines an unfilled rectangle. Xoffset and Yoffset are the        distance from TopX and TopY at which the top left coordinate of        the rectangle is located. Width an Height are the dimensions of        the rectangle. ForeGroundColor is the color of the rectangle and        BackGroundColor is the color behind the text.    -   ‘BitMap’ defines a bitmap and its location. BitMapID is the        Resource ID of the bitmap. Xoffset and Yoffset are the distance        from TopX and TopY at which the top left coordinate of the        bitmap is located. The XferMethod determines how the bits in the        bitmap will be applied.    -   ‘Line’ draws a line from X1offset, Y1offset to X2offset,        Y2offset. X1offset and Y1offset are the distance from TopX and        TopY at which point the line begins. X2offset and Y2offset are        the distance from TopX and TopY at which point the line ends.    -   ‘RoundRect’ defines a rectangle with rounded corners. Xoffset        and Yoffset are the distance from TopX and TopY at which the top        left coordinate of the rectangle is located. Width an Height are        the dimensions of the rectangle. Radius is the radius of the        rounded corners. ForeGroundColor is the color of the rectangle        and BackGroundColor is the color behind the text.    -   ‘Text’ places a text string on the display. StringID is the        Resource ID of the text to be drawn on the display. Xoffset and        Yoffset are the distance from TopX and TopY at which the top        left coordinate of the string is located. Spacing is the number        of blank bits between letters. ForeGroundColor is the color of        the text and BackGroundColor is the color behind the text.        Direction specifies the direction at which the text will be        drawn. The FontID is the Resource ID for the font to be used in        representing the text.    -   ‘ClipRect’ defines an allowable area within the display within        which a drawing may appear. Xoffset and Yoffset are the distance        from TopX and TopY at which the top left coordinate of the        drawing area is located. Width an Height are the dimensions of        the drawing area.

SCROLLCONTROL (ControlName, ControlCode, Left, Top, Right, Bottom,State, TopUpID, TopDownID, BottomUpID, BottomDownID)

SCROLLCONTROL generates a bitmap control which displays a verticalscroll bar with top and bottom arrows. “ControlName” is a SYMBOL. Itsassigned value is the Resource ID for the control. “ControlCode” is thevalue generated when the control on the touchscreen is pressed orreleased. “Left” is the left most X coordinate of the displayed control.“Top” is the upper most Y coordinate of the displayed control. “Right”is the right most X coordinate of the displayed control. “Bottom” is thelower most Y coordinate of the displayed control. “State” is the defaultsettings for the state flags. “TopUpID” is the Resource ID of the toparrow bitmap that is drawn on the display when the control is active butnot pressed. “TopDownID” is the Resource ID of the top arrow bitmap thatis drawn on the display when the control is active and pressed by theuser. “BottomUpID” is the Resource ID of the bottom arrow bitmap that isdrawn on the display when the control is active but not pressed.“BottomDownID” is the Resource ID of the bottom arrow bitmap that isdrawn on the display when the control is active and pressed by the user.

TEXTBOXRESOURCE (ControlName, ControlCode, Width, Height, Left, Top,Right, Bottom, ScrollID, StringID, FontID, Box, Type, Radius)

TEXTBOXRESOURCE generates an allowable area on the display for text andan optional scrollbar and fills the area with scrollable text.“ControlName” is a SYMBOL. Its assigned value is the Resource ID for thecontrol. “ControlCode” is the value generated when the control on thetouchscreen is pressed or released. “Width” and “Height” are thedimensions of the text box, including the scroll bar. “Left” is the leftmost X coordinate of the displayed control. “Top” is the upper most Ycoordinate of the displayed control. “Right” is the right most Xcoordinate of the displayed control. “Bottom” is the lower most Ycoordinate of the displayed control. “ScrollID” is the Resource ID ofthe scroll control used in the text box. “StringID” is the Resource IDof the string that is drawn when the display is first shown. “FontID” isthe Resource ID of the font with which the string is drawn. “BoxID”specifies that the box will not be drawn or will be drawn with square orrounded corners. If rounded corners are specified, “Radius” defines theradius of the rounded corners.

Turning to FIG. 4, the Operating System (OS) 400 software that the MainProcessor 101 executes is organized into several units called Managers.Each Manager performs a specific task when called upon by the OS 400.The following are exemplary Managers:

-   -   The Memory Manager 402 allocates blocks of memory and resources        for use by an application program 434.    -   The Display Manager 404 controls what is shown on the LCD (180        in FIG. 3). It can control what is shown over the entire LCD or        just a portion of it. The Display Manager 404 generates a        display based primarily on specified Resources held in memory.        The display can, therefore, be modified by changing the content        of the Resource rather than by changing the Display Manager code        404.    -   The Control Manager 406 creates and destroys controls as well as        handles the user responses to the interactive graphical controls        displayed on the LCD. When a user selects a graphical icon shown        on the LCD, the Control Manager 406 responds to the Event and        may alter the graphical display in response to the user action.        All icons and graphical entities displayed by the Control        Manager 406 originate as a Resource and may, therefore, be        changed.    -   The Graphic Manager 408 is responsible for the actual drawing of        the entities shown on the display. It also loads the alphabetic        fonts used for text in the display.    -   The Event Manager 410 will queue or mask Events that arise        during the operation of the remote control 10. These Events        include user interaction with the touch screen 24 or key pad 20        and system Events generated by timers or by any of the        communication ports. Events in the queue are accessed by        Application Software 434.    -   The real-time clock (RTC) Manager 412 generates a periodic        timing mark as an Event. It may also be adapted to keep the        current time.    -   The Touch Manager 414 generates an Event each time the touch        screen 24 is touched and sends the Event to the Event manager        410.    -   The Communication Manager 416 handles all serial messages        between the Applications 430 or other Operating System software        modules and those peripherals connected on the serial buses such        as the infrared controller 140, and the ADC and touch decoder        170.    -   The RF I/O manager 418 handles all two-way data communication        between Applications 430 and remote resources such as server        applications running in other devices (PCs, set top boxes, TV        sets, CD jukeboxes, etc.).

To communicate to systems beyond those devices conventionally found in ahome entertainment system, the remote control 10 provides a two-wayinfrared or two-way RF system (or other communication technology). Usingthis communication technology, the remote control 10 can access,process, and/or display data from remote sources. The RF I/O manager 418(or IR I/O manager in the event a two-way IR communications path is usedinstead) accepts data from Applications 430 running under the OS andprepares the data for communication by splitting the data into packetsand adding packet header information. It also accepts received packets,ensures packet integrity and assembles the received packets into data tobe sent to the Application(s) 430.

The RF I/O manager 418 interacts directly with the two-way RF hardwarepreviously described (e.g., RF controller 120 and RF transceiver 130).Checksums are appended to outbound data and the packets are sent.Inbound data is received from the communications hardware. Error freepackets are passed to the Application interface and a confirmation ofsuccessful reception is sent to the originator. Packets with errors arediscarded and up to three retransmit requests can be sent to theoriginator.

In one preferred embodiment, the data communication protocol implementedby the RF I/O Manager 418 comprises communication packets which cancarry data or commands. Each packet comprises a header and the attachedcommand or data. Commands are transfers of non-data and are acted upon.A sequence is any number of packets that comprises an entire transfer ofdata, such as a complete text stream, a complete bitmap file, a Web pageor any other complete data resource. A block is a series of datapackets. A single block or multiple blocks may constitute a sequence. Anexemplary Communication Packet format is illustrated in Table 1 below.

TABLE 1 Field Bytes Description Byte Count 1 Total number of bytessupplied to the end of the data (7 + n) To Address 2 The address of thereceiving station (usually the server). From Address 2 The address ofthe Remote Control platform Packet Number 1 Bits 0-6 are used to be sureevery packet is sequential. Most significant bit used to indicate acommand packet (MSB set). Port Number 1 Used to keep track of multipledata streams. Data n Packet payload - data or command

The Byte Count is the total number of bytes in the packet, including theheader. The To Address is the address of the receiving station (usuallya server or gateway). The From Address is the address of the remotecontrol 10. The Packet Number is used to ensure every packet issequential. The Most Significant Bit of the Packet Number indicates acommand packet when set to a Logic 1. A unique Port Number can beassigned to each unique data sequence, so that packets of differentsequences can be transmitted in an interleaved fashion. Each separatestream of data packets should have its own port number as well as itsown packet number sequence.

In one embodiment, six commands are defined for use by the remotecontrol 10. The payload data of each command comprises a one bytecommand code followed by a variable number of parameters, as:

-   -   STX (data=0x02h). The STX command indicates the start of the        transmission of a series of packets comprising a data sequence.        This command is accompanied by parameters which specify the        total number of packets in the sequence and the Port Number        assigned to the sequence. Once an STX command is answered by an        ACK, any communication using the specified Port Number will be        associated with that specific “sequence” of data.    -   ETX (data=0x03h). The ETX command follows after a complete        sequence has been transmitted, and contains the checksum for the        entire sequence (excluding the headers). If a NAK is sent as a        reply to an ETX command it is meant to signal retransmission of        the entire sequence.    -   ACK (data=0x06h). The ACK command signals a successful transfer        of a data Block or Sequence.    -   NAK (data=0x15h). The NAK command signals an unsuccessful        transfer of a data block or sequence. NAK also constitutes a        request for retransmission of the data not correctly received.    -   ETB (data=0x17h). The ETB command indicates the end of a block        of data. Also causes the packet sequence count to be reset to        zero.    -   CAN (data=0x18h). The CAN command cancels the sequence on the        Port Number included in the data portion of this command.        While the above describes one possible implementation of a        communications protocol for transfer of data between the remote        control 10 and another device, it will be appreciated that there        are many other possible protocols that are equally suitable        including, but not limited to, those corresponding to various        standards, e.g. Bluetooth, IrDA Control, IEE802.11 and others.

To effect the transmission of IR codes, the IR controller 140communicates with applications 430 resident in the remote control 10using a pre-defined set of commands. Since the actual mechanisms andformats for transmitting such IR signals are well known in the art—see,for example, U.S. Pat. No. 4,959,810 which is incorporated herein byreference in its entirety—it will not be described further herein. In anexemplary embodiment, the SendIR command is issued to the IR Controller140 to cause an IR code to be transmitted. The SendIR command may be asix byte packet including the fields RcdLength(1), 01h,DeviceTypeNum(2),KeyCode(1) and KeyFlag(1) where:

-   -   RcdLength is a one byte value indicating the total number of        bytes in this packet.    -   01h is a command type which identifies this command as a “send        IR” command.    -   DeviceTypeNum is a combination of DeviceType and DeviceNumber as        follows:        -   Bits 15 . . . 12: DeviceType—see Table 2 below.        -   Bits 11 . . . 0: DeviceNumber represents a four (decimal)            digit number which identifies a set of IR functions to            control a specific device (e.g. “Sony TV set”)    -   KeyCode identifies the function to be transmitted, according to        Table 3 below.    -   KeyFlag indicates if any special processing is required. For        example, if KeyFlag bit 7 is “on” this can indicate that this IR        command is part of a macro sequence playback, requiring that the        IR data frame be repeated a certain minimum number of times. If        bit 5 is “on” this can indicate that the IR Controller should        use a learned IR code rather than its pre-programmed code.

TABLE 2 IR Controller device types Letter Device Type Device NameRepresentation 0 TV T 1 Cable C 2 Video Accessory N 3 Satellite/DSS S 4VCR V 5 Cassette Tape K 6 Laser Disk L 7 Digital Audio Tape J 8 DigitalVideo Disk Y 9 Tuner/Amplifier R 10  Amplifier/Misc. Audio A/M 11 Compact Disk D 12  Phonograph P 13  Home Control H 15-31 Reserved

TABLE 3 IR Controller KeyCodes KeyCode Function Name  1 Digit 1  2 Digit2  3 Digit 3  4 Digit 4  5 Digit 5  6 Digit 6  7 Digit 7  8 Digit 8  9Digit 9 10 Digit 0 11 Volume Up 12 Volume Down 13 Mute 14 Channel Up 15Channel Down 16 Power 17 Enter 18 Previous Channel 19 TV/VIDEO 20 TV/VCR21 A/B 22 TV/DVD 23 TV/LD 24 Input 25 TV/DSS, TV/SAT 26 Play 27 Stop 28(Search) Forward 29 (Search) Reverse 30 Pause 31 Record 32 Menu 33 MenuUp 34 Menu Down 35 Menu Left 36 Menu Right 37 Select 38 Exit 39 . . .255 Other functionsIt will be appreciated that there are many other commands that go backand forth between the processors and that the above description withrespect to the SendIR command is not intended to be limiting.

As noted previously, the exemplary remote control hardware and operatingsystem are capable of supporting multiple application programs. In apreferred embodiment, two application programs coexist in the unit: onewhich provides conventional remote control (“clicker”) functionality432, and another associated with the two-way RF communication subsystemwhich provides general purpose text and graphics display capability inthe form of a compact browser utility 434. The application whichprovides conventional consumer appliance remote control functionality ispreferably the application that is launched by default upon power-up(i.e. insertion of batteries into the unit) and is the mode of operationmost commonly used by the user.

FIG. 1 illustrates a typical appearance of the LCD touch screen 24 whenthe remote control 10 is in the mode of operation for providing remotecontrol functionality. It will be appreciated that many other displaysare also available, depending on the type, model, and functionality ofthe device(s) to be controlled. In addition, the remote controlapplication need not display key icons for functions not supported by aparticular device, so the actual display may vary according to thespecific device brand or even model currently set up. For example, eventhough the IR controller and the remote control screen layout may ingeneral support menu operations (see KeyCodes 32 through 38 in Table 1),if the specific device currently set (e.g. a Goldstar TV) does not offerthis feature, those keys need not be displayed.

Turning now to FIG. 5, FIG. 5 illustrates the top level programhierarchy within the remote control application 432. The remote controlapplication 432 (and it's sub-applications) acquire Events from an eventqueue (placed there by the Event Manager 410) and use other Managers andResources to perform their intended function. The main menusub-application 500 is called at the time the remote control 10 receivespower, for example, the time at which the batteries are installed. Itinitializes all the Managers 400, places a welcome message on the LCDdisplay 24, initializes and loads all Applications and Resources thatmay be used. After a set period of time (a few seconds), the welcomemessage should be replaced by the default device screen. A typicaldefault device screen is shown in FIG. 1.

Once all Applications and Resources have been initialized, the main menusub-application 500 waits for an Event. One such Event is an internalmain processor timeout which, in this specific case, turns off thedisplay and system CPU to save battery power. Another such Event is auser key press. In this latter case, the user may press one of severaltypes of keys, creating Events to which the main menu sub-Application500 responds. One or more of the control keys shown on the display 24generates an Event invoking a sub-application 503 that produces a newdisplay. Typically this might be a second “page” (i.e. alternativedevice screen) of command keys for the current device under control(e.g. a TV) or for a different device (e.g. from TV to VCR) with a newpage of keys. Activation of another group of keys (both the soft keysshown on the display and the hard keys in the keypad 20) will invoke asub-application 504 that transmits an infrared code. The send IRsub-application 504 communicates with the IR controller 140 via theoperating system's communication manager using the IR controller commandstructure described earlier to cause the appropriate device IR commandsignal to be transmitted.

Activation of other keys can invoke a sub-application 502 that will turnon the display backlighting. It will be appreciated that a motion sensorcould also be used to turn on the display backlighting, for example,when the remote control 10 is picked up. Yet another key activation caninvoke the setup sub-application 501 that permits the user to customizethe remote control 10. Activation of still other keys can invoke adifferent application 508 and pass control of the unit to thatapplication. By way of example, activation of a key 41 labeled “iMosiac”may invoke the Browser application 434 which is described in greaterdetail below.

For customizing the universal remote control 10, the setup Application501 is invoked. Customization, as is shown in FIG. 5, can be provided bythree menu-driven, sub-applications, namely, the device personalizationsub menu 505, the device setup sub menu 506 and the system sub menu 507.The device setup sub menu 506, shown in FIG. 6, comprises fivesub-applications that afford the user the opportunity to access all ofthe infrared control codes required for operation of an entire homeelectronics system. Control codes may be pre-stored in the main memory110 or the IR Controller 140 of the remote control 10, learned into themain memory 110 by using the remote control that was supplied with adevice, or downloaded from a remote source, e.g., from a source via theInternet.

To select control codes to be available for access to control consumerelectronic devices by device type and manufacturer, the setup by brandsub-application 510 is utilized. This sub-application is based in parton technology disclosed in U.S. Pat. No. 5,614,906 entitled “Method forselecting a remote control command set” that is incorporated herein byreference in its entirety. The setup by search sub-application 516permits the user to select control codes by linearly stepping throughthe data base of codes by device type, trying each one in turn. Thesetup by code sub-application 513 permits the user to simply enter aknown code number to configure the remote control 10 to make accessiblethe control codes to control the device(s) corresponding to the knowncode number. The new code sub-application 519 allows the user to try newcodes received during a prior download over the Internet or throughcustomer service via the telephone. Selected/downloaded control codesmay be made available for user access by using the add function 511 orused to replace currently accessible control codes using the replacefunction 512. The delete sub-application 522 can be used to erase allselected control codes, allowing the user to start over with a cleanslate.

The personalization sub menu 505 of sub-applications shown in FIG. 7offers some very powerful sub-applications to the user that permit theremote control 10 to be fully personalized to meet specific needs of auser. For example, the macros sub-application 530 comprises fivedifferent functions. The macros sub-application 530 is based ontechnology disclosed in U.S. Pat. No. 5,959,751 entitled “UniversalRemote Control Device” which is incorporated herein by reference in itsentirety. The macros sub-application permits the user to add 531, view532, delete 534, copy 533 (e.g., onto another screen) or delete all 535macro functions.

To select a key from one device representing a specific infraredfunction and create a copy of it for use with another device, the movekey sub-application 540 is utilized. For example, the move keysub-application 540 can be used to move the channel up function for theTV device such that it is accessible from the VCR device screen. ThisSub-Application is based on technology disclosed in U.S. Pat. No.6,014,092 entitled “Key mover” that is incorporated herein by referencein its entirety. In addition to moving a key 541 a user may delete all542 keys that have been moved.

To teach the remote control a new function from another remote control,the learn sub-application 550 is utilized. The learn sub-application isbased on technology disclosed in U.S. Pat. No. 6,097,309 entitled“Remote control learning system and method using signal envelope patternrecognition” that is incorporated herein by reference in its entirety. Anew function can be learned 551 by the remote control and assigned to apre-defined function key or to a blank key. All learned functions can bedeleted 552.

To label new device keys 561, new function keys 562 or to edit existingkey labels, the label keys sub-application 560 is utilized. The labelkey sub-application 562 makes available symbols and lower and upper casecharacters as well as the backspace, space, and shift for use increating alphanumeric key labels. A caps lock function can also beprovided.

To teach the remote control a new function by entering a code, the keymagic sub-application 570 is utilized. The key magic sub-application 570is based on technology disclosed in U.S. Pat. No. 5,515,052 entitled“Universal remote control with function synthesis” that is incorporatedherein by reference in its entirety. A new function can be added 571 andassigned to a pre-defined function key or to a blank key. All addedfunctions can be deleted 572.

Any key on any device page may be viewed and deleted by the view &delete function 595.

The volume lock sub-application 580 affords the user a means forcontrolling the volume for one device (the amplifier, for example) fromanother screen dedicated to controlling another device like the TV, forexample. The user may institute the locking feature using the lockfunction 581 or may remove the feature using the unlock function 582.

The home theater sub-application 590 offers the user a means forcreating on one or several screens a set of keys that are those mostoften used keys in a home theater system. The user may configure thefeature using the configure function 591 or may remove the feature usingthe reset to default function 592.

The system sub menu 507 of sub-applications, illustrated in FIG. 8,offers the user the ability to affect the overall operation of theremote control. For example, the upgrade sub-application 600 permits theuser to add 601 codes from a remote source such as a server on theInternet, via a cable set top box, etc. This application makes it easyfor the user to always have the most current and/or correct codes in thesubject remote control, even after the purchase or upgrade of newdevices for the family home entertainment system. This sub-applicationmay be based on technology disclosed in U.S. Pat. No. 5,537,463 entitled“Magnetic modem in a remote control,” U.S. Pat. No. 5,228,077 entitled“Remotely upgradable universal remote control” and in U.S. Pat. No.5,689,353 entitled “Remote control with two-way data coupling” that areincorporated herein by reference in their entirety. The add function 601and the replace function 602 make it possible for the user to add orreplace codes after the upgrade process is complete.

The LCD sub-application 610 provides a means for the user to compensatefor any drift in the calibration of the LCD 24 during long-term use. Theuser may invoke the calibrate function 611 to return the LCD 24 tofactory-level settings.

While using the touchscreen 24, the user can receive audible feedbackthat a key has been selected. To this end, a soft clicking sound isissued by the speaker or by the buzzer 102. This sound may be turned onor off using the sound on/off sub-application 630.

After the user has fully personalized the subject remote control, thosesettings may be locked into place to avoid inadvertent changes. Thisfeature is performed by the lock on/off sub-application 620. The usermay return the remote control 10 to its original, factory settings byinvoking the user reset/master reset sub-application 640.

To navigate and browse HTML-formatted data supplied from an externalsource (e.g., via a two-way RF or IR communications link) the remotecontrol 10 includes a browser application 434 that supports a sub set ofXHTML-Basic and Compact HTML as proposed and defined by the World WideWeb Consortium. In this manner, the remote control 10 provides forcustomized user interface and data display since, within the constraintsof the remote control hardware (screen size, color, memory availability,etc.), any screen layout of text, images, and/or hyperlink buttons ispossible. Thus, any external device equipped with a compatible RF or IRtransceiver, such as a personal computer, cable or satellite set topbox, home automation controller or security system, CD jukebox, TV set,and the like, can avail itself of the remote control 10 as a datadisplay and interface device via a well-understood standardized set ofHTML commands.

In addition to the subset of XHTML-Basic commands supported, the remotecontrol browser can also offer extra META statements as specialextensions of the standard to facilitate use in situations which are notclassically Web-based. For example, the browser can support a “Fullscreen” META statement, <META NAME=“Any Names” CONTENT=“Full Screen”>,that will cause the browser to go to full screen display mode (e.g., nonavigation buttons or scroll bars are displayed). Similarly, the browsercan support a “Refresh” META statement, <META HTTP-EQUIV=“Refresh”CONTENT=“xx; URL=http://www.name.com/anything.html”>, that will causethe Browser to count a given number of seconds, as specified in the“content field,” and then display the next html page specified, or ifthe “URL=” is not present, refresh the current page. Both of theseextensions are useful for authoring displays in which the user is notnecessarily aware that the interface presented to him is HTML based viaa browser—for example, simple TV guide applications and the like.Additionally, the “Refresh” feature is useful in applications where thedata content to be displayed on the remote control 10 needs to besynchronized with a TV or audio program, for example enhanced TVservices or karaoke lyrics.

The browser application can also be adapted to support a specialextended HTML tag type, “IROP.” With this ability, the remote control 10can be used in connection with HTML pages that are authored to support“buttons” for use in sending IR commands. The general format of the IROPtag is <IROP KEY=“1-18, . . . ”, LABEL=“function name” IMG=“file path”>where the “KEY=xx,yy . . . ” field contains data indicative of an IRcode to be transmitted. In this regard, the data could specify the IRcode(s) to be transmitted upon activation of the button using the IRKeyCodes defined for the IR controller defined in Table 3 above.Alternatively, the field could contain data representative of the actualIR code to be transmitted using a formatting technology such asdescribed in U.S. Pat. No. 5,515,052 which is incorporated herein byreference in its entirety. The “LABEL=” and “IMG=” fields respectivelydefine a label and graphic (i.e. icon) associated with the button orlink. For example <IROP KEY=“10, 7”, LABEL=“ABC”> would result in thedisplay of” “ABC” as a selectable area on the screen. User activation bypressing the “ABC” area on the touch screen would cause the browser tosend to the IR Controller 140 a SendIR command containing KeyCode number10 followed by a SendIR command containing KeyCode number 7, thuscausing the IR Controller to transmit the IR codes for the digits “zero”and “seven,” i.e., selecting channel 7 on the current consumerelectronic device used for channel changing (TV, Cable box, Satellitereceiver, etc.).

As will be appreciated, this extended IROP tag is useful in situationswhere it is desired that a user be provided with the ability to interactwith an HTML page to initiate the transmission of IR command codes toconsumer appliances. Examples of such HTML pages include TV guides, CDjukebox managers, and the like. Furthermore, it is contemplated that theIROP tag could be used to present to a user a virtual remote controlthat has the key layout and appearance of a prepackaged remote control(e.g., a display presenting a key layout and appearance of a Sony remotethat is prepackaged with a Sony TV). In this manner, activation of alink having an IROP tag on the virtually displayed remote control (i.e.,selection of a virtually displayed control key) can cause the remotecontrol 10 to transmit the same control code as if the user whereactually activating the corresponding key on the prepackaged remotecontrol.

The remote control can be further adapted to support another specialextended HTML tag type “MREM.” With this ability, the remote control 10,if equipped with a date/time clock capability, can support areminder/calendar feature used in connection with HTML pages that areauthored to supply data regarding upcoming events. The general format ofthe MREM tag is <MREM TTR=“Time to Remind” LABEL=“Note/Memo” IMG=“filepath” LINK=“URL”>. This tag will cause a calendar event to be registeredwith the Remote Control application where TTR represents the time at orafter which a reminder message is to be displayed during normaloperation of the remote, LABEL represents the message to be displayed atreminder time, IMG (optional) represents an image to be displayed atreminder time, and LINK (optional) specifies the URL of an HTML page tobe automatically loaded at reminder time. Note that if the LINK optionis specified, this will also cause the Remote Control application toautomatically invoke the Browser application to load and process thespecified URL. With the exception of TTR, any of the fields specifiedabove for the MREM tag may be omitted, i.e. “null,” as required. Forexample <MREM TTR=“5-15-2001-14:45” LABEL=“Watch ‘Who wants to be aMillionaire’”> would result in the reminder text message “Watch ‘Whowants to be a Millionaire’” being displayed at or after 2:45 pm on May15, 2001. Further examples of the application of this HTML tag arediscussed later.

Turning to FIG. 9, to invoke the browser application, the user may, forexample, press a soft button 910 (such as “iMosaic” 41 on the regularremote control application display screen 24). When invoked, the browserapplication starts by initializing itself and the two-way communicationinterface 912 (via the RF I/O Manager in the illustrative embodiment).If the browser application and two-way communication interface aresuccessfully initialized, the remote control 10 displays the basicBrowser screen layout, an example of which is shown in FIG. 11, andissues a request to load a preset home page 914, 916. FIGS. 10 a through10 g provide flowcharts depicting an overall operation of the exemplaryBrowser Application, showing how subsequent processing of the downloadedHTML data can be performed.

Turning to FIG. 10 a, there is shown the overall flow of the exemplaryBrowser application. As described earlier, the remote control 10 is anevent-driven system, so once initialized, the Browser Application simplywaits for an Event to occur 1002. Browser-related Events can beclassified into one of three general categories: KeyDown Events 1004which result from user activation of any of the keys shown in FIG. 11(hard or soft); HTML Events 1006 which result from user activation of anHTML generated item in the current display area (for example ahyperlink, check box, text input area, etc.); and I/O Events 1008resulting from activity on the two way communication link, timers, orother system-generated interrupts (a low battery indication, forexample). The individual processing of each of these categories of Eventwill be described in further detail below in conjunction with thefigures that follow.

In one exemplary embodiment, internal priorities within the BrowserApplication are arranged such that, while in the process of loading anddisplaying a page of data via the RF link, it will ignore other inputssuch as HTML Events. In other words, it is designed such that a user isrequired to wait until the current page is completely displayed beforeinitiating any action such as a hyperlink selection. This is evident inFIG. 10 a where the “IDLE” status of the Browser application (i.e., notcurrently loading data via the RF link) is used to determine whetherKeyDown and HTML events are processed or not. It will be appreciatedthat other implementations are also possible, in particular, providingthe ability to abort an HTML download in progress and initiate a new oneby pressing a key or hyperlink in a partially loaded and displayed page.

FIG. 10 b depicts the processing of a KeyDown Event, specifically theaction taken in response to each of the possible key press user inputs.As can be seen, these actions are used to effect page navigation andbrowser control in addition to providing a means to configure theBrowser Application and to return the unit to the (default) RemoteControl Application.

FIG. 10 c depicts the processing of an HTML Event. In the HTML subsetsupported by the exemplary Browser Application, only four classes ofHTML Events can occur: Activation of a hyperlink 1010; activation of aform control field 1012; expiration of a “refresh” META statement timer1014 (a special extension to standard HTML which allows periodicreloading of a page); or activation of a IROP field 1016 (a specialextension to standard HTML which allows IR commands to be transmitted toconsumer appliances). Activation of a hyperlink results in a request forthe contents of the specified URL to be issued via the communicationslink, after which the Browser Application returns to the “Get NextEvent” waiting state shown at the top of FIG. 10 a pending receipt ofthe requested data. Activation of a forms control function results inthe appropriate action as shown in FIG. 10 b (note that not all possibleHTML forms functions are supported by the subset and, therefore,unrecognized control requests may be ignored), again followed by areturn to the “Get Next Event” waiting state. Expiration of a “refresh”timer causes a request to be issued via the communications link for theURL specified in the META statement (or, if no URL is specified, thecurrent page to be automatically reloaded) and a return to the “Get NextEvent” waiting state pending receipt of the requested data. Activationof an IROP control causes the Browser to issue SendIR commands to the IRController, as described earlier, also followed by a return to the “GetNext Event” waiting state.

FIG. 10 d depicts the processing of an RF I/O Event. All communicationstransactions are preferably timed in order to allow appropriate actionto be taken by the Browser in the event the communications link isinterrupted, for example by the user wandering out of RF range. Thus,the first I/O Event that is checked for is a timer expired status 1020.If there is a Port currently open (i.e. activity in progress) the timerexpired event is handled as shown in FIG. 10 e, described in more detailbelow. If the Event is an “RF Buffer Ready” event 1022, indicating thatthere is received data ready for processing, the event is handled asshown in FIG. 10 g, described in more detail below. An RF bufferoverflow event 1024 signifies an error condition, handled as shown inFIG. 10 f, described in more detail below. If the sending (server) sideissues a “Cancel” command (a request to abort transmission), this event1026 is handled in a similar manner to a timeout event. All other typesof events 1028 represent conditions which should abort any page downloadcurrently in progress (e.g. a low battery condition), and thus result inthe Browser issuing a “CANCEL” request to the server (the inverse of theserver “CANCEL” described previously) provided a Port is currently open.

FIG. 10 e shows the error processing invoked in the case of a timeout ora server initiated “CANCEL” request when the Browser application is not“idle,” i.e. it is loading HTML or image data via the RF link. If agiven time, e.g., three seconds, has not elapsed since the last activityon this port 1030, timing continues without any action. If the giventime has been reached or exceeded, the Browser issues a “CANCEL” requestto the server 1032. It then determines if a given number of retries,e.g., three, have already occurred for this particular request 1034. Ifthe number or retries has not been exceeded, the Browser reissues therequest 1036. If all of the retries have been exhausted, the Browsertakes error action as appropriate: in the case of a failed HTML pagedownload it may display an error message to the user 1038 (FIG. 21 is aexample of such a message); if the failure occurred during the downloadof an image 1040, the Browser may simply skip display of that image andproceeds to request the next image 1042, if any exists. (The processingof HTML and requests for image data is described in more detail later inconjunction with FIG. 10 g.)

FIG. 10 f shows the error processing that occurs in the event of abuffer overflow. As can be seen, the actions taken by the remote control10 are similar to those described above in conjunction with an exhaustedretry count.

FIG. 10 g shows the processing steps that occur upon receipt of a bufferfull of data Events from the RF I/O Manager. In this case, the Browserfirst checks its internal status to determine if it is currentlyexpecting HTML or image data 1050. If expecting HTML data, the HTML pageis sent to the HTML parser 1052, which processes the HTML data andbreaks it down into individual elements for display (text strings andimages), position coordinates for each hyperlink or control within thedisplay, and a table of control-link relationships. The HTML parser alsosets the appropriate timer if a “refresh” META statement is encountered.When the HTML parser has completed its analysis, the display informationis passed to the Display Manager 1054 for rendering on the LCD screen.Once the basic HTML page is displayed (i.e., text, links, controls, etc.together with “place holder” icons for the locations of graphic images)the Browser may then issue requests for any graphic images called out inthe HTML source, loading and displaying the graphic images one by oneuntil all specified graphics have been displayed. This is achieved byissuing a request for the next graphic file 1056 via the RFcommunications link and then returning to the “Get Next Event” state(FIG. 10 a).

When a response is received, the next RF buffer ready Event will findthe Browser in an “expecting image data” state. This will cause theopposite branch to be taken at the top of FIG. 10 g. Here, the Browser,after making any necessary adjustments to page layout resulting from theinsertion of the new graphic 1058, displays the graphic data justreceived 1060 and issues a request for the next graphic. In someinstances the graphic size may have been predefined in the HTML, inwhich case no adjustment is necessary since the appropriate area isalready allocated, but in others the final graphic may differ in sizefrom the “place holder” icon and require adjustment to the balance ofthe page layout to accommodate it. After the last graphic has beendownloaded and displayed, the Browser sets its internal status to “IDLE”(thereby enabling recognition of HTML and KeyDown Events) and returns tothe “Get Next Event” state (FIG. 10 a.)

FIG. 11 shows an exemplary, basic touch screen display layout for theremote control Browser. In the illustration, the layout comprises atoolbar 1100 containing the usual Browser control items (e.g., “back,”“forward,” “reload,” “stop,” “go to,” and “home” illustrated from leftto right), a key 1120 to access previously entered bookmarks, a generaldisplay area 1150 in which HTML formatted data is displayed, and ascroll bar 1140 used to navigate pages of data which are longer than thedisplay space. In addition, the screen may include two control elementsspecific to the browser application, namely, a key 1130 to access set uproutines used to adjust items such as RF link addresses, home page URL,etc., and a key 1110 used to return the unit to the basic remote controlapplication 432 when use of the Browser is complete.

The “home page” URL first loaded by the Browser application need not beWeb based in the classical sense. Rather, the “home page” may be anaddress pointing to a locally stored, HTML formatted interface to a homecontrol system as illustrated in FIG. 12. The “home page” illustrated inFIG. 12 shows an example of how the universal remote control 10 candisplay simple icons and messages 1202 useful in receiving informationfrom appliances around the home and, in turn, controlling them. In yetanother example, the “home page” initially loaded might take the form ofa TV guide display loaded from a cable or satellite set top boxincluding program viewing information 1302, as illustrated in FIG. 13.Note that this particular example makes use of the “full screen” METAstatement 1300 as described above to hide the generic browser controls(e.g., “back,” “forward,” “reload,” etc.) from the user.

By way of further example, FIG. 14 illustrates the use of the universalremote control 10 as part of a two-way communication system. In thisillustrated example, the remote control 10 is used as a platform tobrowse the Internet, using a personal computer 1420 as a gateway orproxy server. Requests by the user of the universal remote control 10for access to certain information located on Web pages on the Internetare sent through the RF I/O manager 418 and RF module 125 to a matchingRF transceiver unit 1410 which is attached to the personal computer 1420via one of its serial ports 1415. Software resident in the personalcomputer 1420, including an HTTP interface and server application 1440,formats the request appropriately and forwards it to the specified WebURL. When a response to a request is received at the personal computer1420, the personal computer 1420 performs any format conversion requiredfor compatibility with the subset of HTML supported by the remotecontrol 10, and then forwards it to the remote control 10 via thereverse of the path described above. In this manner, Web content may beultimately displayed on the universal remote control 10.

In the illustrative example, the PC application that provides theInternet access for the remote control 10 is called the serverapplication. As illustrated in FIG. 15, the server start up module 1500is invoked when the server application is started on the personalcomputer 1420. The server application manages the display (to the PCscreen) and internal settings 1510, the transfer of data 1520 betweenthe Internet and the remote control 10, and the external serial port1540 to which the PC-side RF transceiver unit 1410 is attached. Asserial messages are received 1542 they are placed in an internal databuffer 1544 from which they are subsequently processed and delivered tothe Internet 1522,1524,1526. If Internet data is received 1526, then itis converted to a compatible format if necessary 1528, 1530 and thensent to the remote control 10 for display 1532. It will be appreciatedthat while this example uses a personal computer based Web gateway,similar systems can readily be implemented using various other devicesto implement the gateway, for example a cable or satellite set top box,a Web-enabled TV set, a residential home gateway controller, aWeb-enabled game console, a personal video recorder, etc.

Once the universal remote control 10 with two-way communication issuitably installed, many new and heretofore unavailable applications canbe provided. For example, of particular advantage, the remote control 10may be equipped to communicate with an electronic device to retrieveoperating instructions for display on the LCD screen 24 of the remotecontrol 10 as illustrated in FIG. 22. In this manner, instead of aprinted user manual which may be lost, a device 2200 which is alreadyequipped to communicate bi-directionally with the remote control 10(e.g. a cable set top box, a thermostat, a security system, a householdappliance, etc.) has user manual information stored in low cost ROMmemory 2202. To this end, the remote control 10 can be equipped with anapplication 2210 that allows its display 24 to display information thatis encoded using a mark-up language, such as HTML or XML as describedearlier. Thus, the user manual can be formatted using at least a subsetof the mark-up language where it can be retrieved by the user from thedevice (e.g., in response to a keystroke on the remote) and displayed onthe screen 24 of the remote control 10 as needed. In an alternativeembodiment shown in FIG. 23, an appliance 2300, which is not itselfequipped with wireless communication capability can use a wirelesscapable device 2320 as a relay to communicate with the remote control ina similar manner to that described above. In this case, the appliance2300 would have a hardwired (e.g. dedicated wiring, powerline,telephone, video or audio cable, etc.) communication connection 2310 tothe device 2320 which does have wireless capability.

By way of illustration, FIGS. 18 a and 18 b set forth an exemplarymethod by which a thermostat unit might support the above-describedinformation retrieval feature. To initiate the information retrieval,the remote control 10 can transmit a command to the appliance thatsignifies a request for the information. The transmission of theinformation request command by the remote control 10 would normally bein response to the occurrence of an Event at the remote control 10,e.g., the activation of a soft key. Upon receipt of a command at theappliance, the appliance determines if the command is a request forinformation 1810. If the command is a request for information, theappliance can set a flag to indicate that the appliance is in a state ofservicing the request 1812, can retrieve its current operational status1814, and fetch from memory a pre-formatted page that has userinstructions corresponding to the current operational status 1816. Theretrieved information would be transmitted 1818 back to the remotecontrol 10 for display on the LCD 24 as illustrated in FIG. 18 b.

If multiple user instruction pages are stored in memory, the appliancemay further set a pointer to indicate the next page in a sequence 1820.The availability of more information would be indicated to the user inthe displayed user's manual by, for example, a “more” hyper-link orbutton as illustrated in FIG. 18 b. It will be appreciated that in theHTML, this “more” function could be associated with either a hyper-linkin the conventional HTML sense, or with an IROP tag to cause an IRcommand to be transmitted, depending on the requirements of theparticular appliance. In either case, if the user causes the remotecontrol 10 to issue a command requesting the next page of information1822 by activating the “more” key, the appliance will retrieve the nextpage of information from memory 1824, transmit 1818 the page informationto the remote control 10, and update the page pointer 1820, ifnecessary. If the command received by the appliance from the remotecontrol 10 is not related to the retrieval of the user's manual from thememory of the appliance, the command will be processed by the appliancein accordance with its operating instructions 1826.

In an alternative embodiment, once the make (and also possibly themodel) of the device has been entered into the remote control 10 (eitherby direct interaction with the device or by a process of deduction basedon the setup number input by the user to control the device) the usermanual could be obtained via an Internet connection (using a Web sitespecific to the manufacturer or a generic compilation maintained by athird party). For this purpose, the remote control 10 would use thebrowser functionality, in conjunction with Web access via a personalcomputer, set top box, or the like, as previously described. In thiscase, if the model of the consumer appliance were important to whichuser manual were to be displayed (i.e., multiple user manuals formultiple models of appliances), and only the make of the consumerappliance were provided, the Web site could offer a list of selectablemodel numbers and/or pose one or more questions to the user by whichquestions it could be deduced which user manual the Web site shouldprovide to the user (e.g., does your TV support PIP, etc.).

By way of further example, FIGS. 19 a and 19 b illustrate one method bywhich the remote control 10 might support Web based retrieval of auser's guide. In the illustrated embodiment, the Remote ControlApplication is provided with a soft key (labeled, for example, “Info”)which causes the Application to retrieve 1910 the current device set upinformation, i.e., the code number provided by the user via one of themethods described earlier in conjunction with the setup sub-application501, and invoke the Browser Application using this information as aparameter 1920. Once the Browser Application is invoked, the Browser canissue a request via the Internet to retrieve the Web pages correspondingto the user's manual for the device indicated by the device set-up codenumber 1922. To this end, the Browser application might consult a URLlook-up table stored in memory that functions to map URLs of Web pageswith the devices cross-referenced by the device set-up code numbers. Asan alternative to storing a URL look-up table in local memory theBrowser application might first access a separate URL that itselfcontains such a table. In either case, once the URL corresponding to thespecific device user's manual has been located, the initial Web pageretrieved from that Internet site would generally comprise a Main Indexpage 1930 having hyper-links 1932 to Web pages 1940 that contain furtherdetailed information, an example of which is illustrated in FIG. 19 b.

In yet another alternative embodiment, the Browser Application, startingwith an internally stored HTML page, could present the user with a menuof devices 2000 for which instructions are available as illustrated inFIG. 20. Depending on the item selected by the user, HTML links 2002associated with the menu of devices 2000 could point to further internalpages which initiate a download from a local device using for example anIROP tag (or it's RF equivalent) in the manner described in conjunctionwith FIG. 18 above. Alternatively, links can be provided that point toexternal, Web-based sources for the user information in the mannerdescribed in conjunction with FIG. 19 above.

Providing the remote control 10 with browser capabilities has furtheradvantages. For example, the remote control 10 could access Web sites,via a set top box, an adapter connected to a PC (especially in homeswhere the PC is always connected to a network, for example, by way of acable modem or DSL-based Internet connection), directly to an ISP(provided the remote is equipped with a modem) or other gateway deviceto gather information, such as, weather, stock quotes, movie reviews,etc., as illustrated in FIG. 16, in the manner previously described inconjunction with FIGS. 14 and 15.

In a further embodiment, the display 24 of the remote control 10 couldbe used to display television viewing guide information, withpersonalization and/or reminder capabilities. Such guide data may beobtained directly from an Internet server, using a local PC, set topbox, home gateway or the like as a proxy server as described inconjunction with FIGS. 14,15 and 16. The guide data may also beretrieved from data locally resident in a PC or set top box thatperiodically obtains and stores guide information by, for example,dialing a pre-determined number or accessing a particular Web site everynight. In either case, the TV guide data, formatted into a compatiblesubset of HTML, is transmitted to the remote control for display at therequest of the user. One such form of display is shown, together withthe HTML that generated it, in FIG. 13. An alternative form fordisplaying guide information is shown in FIG. 27. While additionalcapabilities will be described in conjunction with FIG. 27, it will beappreciated that, since these displays are created by HTML source pages,many other layouts offering equivalent functionality are also possible.

Turning to FIG. 27, FIG. 27 shows a “list” guide 2710 in which theprograms available at a selected time and date are listed, in channelnumber sequence, for multiple TV channels. Alternative arrangements ofthis list are possible, for example, displaying listings for a channelrather than for a time (i.e., all programs to be broadcast by a selectedchannel are listed in a time sequence) or displaying a list that is notsequential by channel number but instead arranged to match a user'spreferences by broadcast channel and/or content type as will bedescribed in more detail later in conjunction with FIG. 30.

To effect rapid selection of a program of interest, the remote control10 can be adapted such that selecting (touching) any of the broadcaststation identifiers 2720 listed on the display 2710 will activate anIROP HTML tag, as described earlier, to cause the remote control toissue the command to switch the TV (or set top box in the case of cableor satellite subscribers) to the corresponding channel. For example, asillustrated in the exemplary embodiment shown in FIG. 27, selecting“PBS” will cause the remote control to issue the commands to cause thecorresponding appliance to switch to channel 10.

The remote control 10 can be further adapted such that selection of thetitle of the program, for example “Clifford Big Red Dog” 2730, willresult in the display of additional information regarding thatparticular program. In this illustrative embodiment, touching one of theprogram names activates an HTML tag which points to other HTML page(s)containing additional information regarding that program. Once again,such additional information page(s) may be resident locally or may beaccessed via the Web. In the example shown, screen display 2750 is theresult of selecting “Clifford Big Red Dog” 2730 on the initial display2710. In this manner television viewing guide information can offer Weblinks to additional information about shows, for example movie reviews,that are accessible by an individual user using the Web browser withoutdisturbing the TV screen display of the program currently being viewedby others.

The TV guide information displayed on the remote control can also bepresented in differing forms to suit the preferences of individualusers. By way of example, FIG. 30 illustrates a system in which theorder of the show listings is arranged according to individualpreferences. In this example, upon initiation of the guide function,users are presented with a screen 3010 which prompts the user foridentifying information, such as a password. Based on the inputreceived, the same TV guide entries may be presented in different orders3020, 3030, 3040 to match the user's individual preferences. While onlya single page of guide information is illustrated in FIG. 30 for thesake of simplicity, it will be appreciated that that this feature is ofparticular utility when the guide information spans multiple pages andthe users are spared excessive paging back and forth by virtue of theirfavorite shows appearing in the first pages(s) of the display.

Another feature also illustrated in FIG. 30 is the possibility of“filtering” listings. For example, a closer examination of the listingdisplay 3040 corresponding to the child “Maggie” will reveal that KCALChannel 9's “Jerry Springer Show” is not listed as a viewing choice forMaggie. Importantly, it should also be realized that although thefeature is illustrated in this example via the sharing of a singleremote control by three different individuals who identify themselves tothe unit with each use, it could equally be implemented using threedifferent remote controls, i.e. each user provided with a personalremote control customized to their particular preferences. An advantageto having the television viewing guide resident in the remote control 10is that it allows such unique features to be offered to the consumer.

By way of further example, in cases where the remote control hardwaresupports a time-of-day clock, the remote control 10 could be used toissue a “missing program” reminder if it detects activity whichindicates that the user is not currently watching TV (i.e., the remoteis in a mode for controlling the operation of a CD player, audioequipment commands being issued, etc. and the user has programmed areminder to watch a particular show). The remote control 10 couldsimilarly be used to remind the user of “tonight's favorite programs”when it detects the user turning the TV on in the evening after apre-determined off” period which indicates that the user was away fromhome. The favorites could be entered by the user or determined fromprevious viewing habits (e.g., by tracking channel selections in timeslots for a given day), etc.

For entering reminders into the remote control 10, an exemplaryembodiment is illustrated in FIG. 27. Turning again to the programdetail display 2750, two exit options are provided to the user. Thefirst exit option, “BACK” 2760, simply returns the user to the previouspage 2710. The second option, “REMIND ME” 2770 is associated with anMREM tag embedded in the HTML. Selection of this option will cause theBrowser Application to extract the date, time, and program informationcontained in the MREM tag and register this data with the reminderfunction of the Remote Control Application for subsequent action asdescribed in further detail later. More specifically, the BrowserApplication will store within a table in memory 110 the informationpertaining to the reminder events. For example, when the Browserapplication encounters <MREM TTR=“5-11-2001-16:00” LABEL=“REMINDER:Channel 10 at 4:00 pm”>, the Browser application would register amessage display 2790 to appear at or near 4:00 pm on May 11, 2001. Thus,the Browser Application populates the table with the date/time, message,image, and URL link information from each MREM tag.

To produce a reminder message 2790 on the standard remote controldisplay 24 at an appropriate time, the steps illustrated in FIG. 28 canbe followed. Turning now to FIG. 28, which illustrates an exemplarymethod by which reminder data is subsequently processed by the remotecontrol application, whenever a key (hard or soft) is pressed 2802 bythe user, movement of” the remote control 10 is sensed, etc., the RemoteControl Application first fetches the current time value 2804 andcompares 2806 this value to those contained in the table of reminderdata. If no entry exists in the table with a time value which is earlierthan or equal to the current time, no reminder actions are required andthe Remote Control Application continues 2808 to process the event inthe usual manner. When no reminder actions are necessary, the remotecontrol 10 can erase 2820 any previous reminder messages that had beendisplayed.

If, however, an entry is found in the table of reminder data with a timevalue less than or equal to the current time, the Remote ControlApplication next checks 2810 if the entry in question contains a URLpointer value (as described earlier in connection with the MREM tagdefinition, URL and message fields may be null) and, if a URL pointerexists, the Remote Control Application immediately invokes and passescontrol to the Browser Application 2812 to load and act on the specifiedHTML page. Thus, in this implementation, existence of a URL pointertakes priority over both any reminder message text as well as any remotecontrol action called for by the key press which initiated table scan.It will, however, be appreciated by those skilled in the art that otherprioritizations are possible.

If no URL pointer is present, the Remote Control Application next checks2814 if the reminder table entry is “stale,” i.e., reminders arescheduled for a time more than 30 minutes ago. If so, it simply ignoresthe message, deleting the table entry 2818 with no further action. Onceagain, those skilled in the art will recognize that otherimplementations are possible using a longer, shorter, or even no measureof “staleness.” The 30 minute value in this exemplary implementation wasselected as appropriate for the TV guide reminder feature it is beingdescribed in connection with.

If the entry is determined to be “not stale” or valid, the RemoteControl Application then checks for the existence of any reminderdisplay data, text, or graphic and generates 2816 any reminder messagedisplay required, e.g. 2790. A reminder may also cause the buzzer 102 toemit a sound, providing emphasis to the display. Thereafter, the RemoteControl Application can delete 2818 the reminder table entry it has justacted upon and continue to scan and process any further table entrieswhich may also be eligible for action.

Of particular advantage to this implementation of a reminder feature isthe fact that the remote control logic is able to detect when the unitis in use (e.g., the consumer is pressing buttons, moved the remote,etc.) and thus displays the reminder message when the unit is actuallyin the consumers hand, as opposed to a passive display system dependentonly on a timer where a reminder message would be displayed regardlessof whether anyone is there to see it or not.

Use of the MREM tag is not limited to TV show reminders. When the remotecontrol is used in communication with a PC or home automation server asdescribed in conjunction with FIG. 14, application programs running onthese devices can download appointment reminders, medication schedulereminders, etc. into the remote control via an HTML page in the mannerdescribed above. Equally, set top boxes could download reminders ofspecial features, upcoming pay-per-view events, etc. Further, for use inconnection with home automation applications, the reminder feature ofremote control 10 can be used in conjunction with appliances and homesystems to allow alarms and status messages to be displayed on thedisplay 24 of the remote control 10 (e.g., freezer quit, oven timerexpired, garage door ajar). To this end, the remote control 10 couldperiodically poll appliances or home automation servers and storemessages received in the form of reminder tags to later inform the user(“beep and display”) when the remote control 10 senses activity on thepart of the user—i.e. the remote control 10 determines that it is beinghandled/looked at by a user.

In still another embodiment, the display 24 of the remote control 10could be used to present closed caption text. To this end, a TV or settop box equipped (or retrofitted) with closed caption capability cancommunicate with the remote control 10 to transmit the closed captiondata stream to the remote control 10 instead of the TV screen. Whenclosed captioning is displayed on the screen 24 of the remote control 10it allows one person to utilize the caption feature without affectingthe program display on the TV screen.

To effect the display of close captioning information, the system may bearranged as illustrated in FIG. 25. In particular, the remote control 10is adapted to communicate with a television, set-top box, or like device2510 that has a memory 2520 in which the closed captioning informationto be displayed is stored. In the illustrated example, the closedcaptioning information stored in the memory 2520 of the device 2510 isextracted from an incoming video signal using a tuner 2530 and closedcaption decoder 2540. It will be appreciated that the closed captioninginformation may be included in a vertical blanking interval (“VBI”) ofthe incoming video signal. While the illustrated example shows theclosed captioning information being downloaded to the memory 2520 froman incoming video signal, it is contemplated that the closed captioninginformation can be received from other sources such as, for example, theInternet.

To request that the device 2510 transmit the closed captioninginformation to the remote 10 for display on the LCD 24, the user mayactivate a soft key which will result in the transmission of a closedcaptioning request command from the remote control 10 to the device2510. The transmission of the command can be accomplished using eitherthe IR transmitter or the RF transmitter. Upon receipt of the closedcaptioning request command, as illustrated in FIG. 26, the device 2510determines 2610 if it is currently in a closed captioning transmit mode.If the device 2510 is already sending closed captioning information tothe remote control 10, via, for example, RF communication module 2550,the device 2510 ends this mode of operation, by clearing a flag used toindicate this operational mode 2620. If, however, the device 2510 is notpresently sending closed captioning information to the remote control10, the device 2510 sets the flag 2630 to indicate it has entered theclosed captioning transmit mode of operation. It will be appreciatedthat the effect of this logic is to allow a single command (i.e., remotecontrol button) to toggle the feature on and off by alternate presses.Other implementations are also possible, e.g., separate “on” and “off”buttons. On initially entering the closed caption transmit mode ofoperation, the device 2510 retrieves 2640 a pre-formatted Web page intowhich the closed captioning information will be placed.

To transmit the closed captioning information to the remote control 10from the device 2510, the memory 2520 is accessed to load into thepre-formatted Web page the buffered closed captioning information 2650.The Web page containing the current closed caption information may thenbe transmitted 2660 to the remote control 10. When the device 2510 is inthe transmit closed captioning information mode of operation, the stepsof loading the current closed captioning information into the Web pageand transmitting the Web page to the remote control 10 are repeated asrequested by the remote control 10. This is accomplished by the remotecontrol 10 issuing a closed captioning refresh request to the device2510 which causes the device 2510, upon the receipt of the request 2670,to load the closed captioning information stored in the memory 2520 intothe Web page and transmit the Web page to the remote control 10.

The rate at which the remote control issues such refresh requests isdetermined by the value contained in the special “Refresh” METAstatement in the HTML page loaded at step 2640. The value is preferablyselected to adequately support the closed caption rate while taking intoaccount the battery power consumption of the remote control. It will beappreciated that, in alternative applications where battery life is nota critical factor, for example, where the remote control unit is to bedocked in a recharging base during closed caption display, the refreshinterval can be made very small or even omitted entirely. In thismanner, the remote control is continuously polling the device 2510 whichcan then refresh the display as often as is necessary to accommodate thestreaming of information into memory 2520.

Using the above described procedure, the system can be further adaptedto present “Fast news.” In this regard, a “headline summary” feature canbe implemented by storing the closed caption frames during a newsbroadcast and then displaying the captured frames as a scrollable textfile on the display 24 of the remote control 10. In this regard, thefast news information can be stored in the memory 2520 of the device andaccessed on request. Alternatively, the information could be placed intoone or more Web pages that are transmitted to the remote control 10 andlocally stored for later viewing. Still further, if the set top box orTV is equipped to communicate bi-directionally with the remote control10, additional information about a show or event in progress (e.g.athlete statistics, actor biographies, etc.) could be displayed on theLCD 24 of the remote control 10 without interfering with the mainpicture on the TV screen. The information could be in the form of textor links to Web pages having the content which is accessible via theInternet. Again, this information would be received from an externalsource and transmitted to the remote control 10 by way of the device2510.

The capabilities described above can further be used to allow the remotecontrol 10 to communicate with an electronic device, such as a DVDplayer, CD player, etc. to display individual movie subtitles, karaokelyrics, etc. on the display 24. This information could be transmitted inreal-time or down-loaded and displayed in a manner synchronized with theelectronic media using the procedure above-described. The display can bein paragraphs/verses, line-by-line or word-by-word. Also, since thisinformation is conveyed to the remote control in HTML form, thesubtitles, lyrics, etc. may comprise plain text data, graphic images, ora mixture of both.

In yet another embodiment, FIG. 24 illustrates and application in whichsong lyrics may be obtained from a Web site using a personal computer1420 or a set top box or other device 2510 as a gateway or proxy server.In this case, the first HTML page downloaded 2402 prompts the user toenter a song title. When the user activates the text entry field bytouching within the indicated area, the Browser display can change to akeyboard arrangement 2404 (corresponding to HTML event 1018 shown inFIG. 10 c) to allow entry of text data. On completion of text entry, theuser can touch an “OK” soft button 2406 to return to the previousdisplay (with the text data entered) 2408. Touching a “submit” softbutton can be used to cause the text information to be transmitted backto the proxy server and, thereafter, to the Web site. In response, theWeb site returns an HTML formatted data page to the proxy sever whichpage is transmitted to the remote control 10 to cause display of theappropriate lyrics 2412.

For displaying sub-titles for movies, etc. in a language that is notsupported by the relevant media, the sub-titles etc. can be downloadedfrom a supporting Web site, kiosk, etc. In this regard, the informationcan be downloaded directly to the remote control 10, provided the memoryis of sufficient size, or downloaded to a smart card or other releasabletype of memory. It will be appreciated that, to support this latterdescribed functionality, the remote control 10 can be adapted to includea releasable media reader or be adapted to communicate with releasablemedia reader. Synchronization of the playing of the media and thedisplay of the sub-titles, etc. can be performed manually, e.g., byactivating a key to initiate the reading and display of information fromthe memory at the time the movie, etc. Alternatively, a signal can beissued from the media player which will cause the remote control 10 toautomatically initiate the reading and display of information from thememory at the time the movie, etc. Since a system and method foradapting a remote control to use a smart card is described in greaterdetail in U.S. Pat. No. 6,223,348 which is incorporated herein byreference in its entirety, it will not be discussed further for the sakeof brevity.

Still further, the remote control 10 can be equipped with a bar codereader to facilitate the gathering of information related to programmingthe remote control 10, home appliances/consumer electronic devices, TVprogramming, etc. Alternatively, the bar code digits can be entered bythe user. Use of a bar code to facilitate programming a remote controlto match the consumer's equipment is disclosed in U.S. Pat. No.6,225,938 entitled “Universal Remote Control System with Bar Code Setup”which is incorporated herein by reference in its entirety. In addition,use of a bar code reader allows the remote control 10 to retrieveinformation indicative of an item/article and, thereafter, displayinformation relevant to the item/article (e.g., instructions, warnings,nutritional info, spare part lists, command codes for controlling itsoperation, etc.). Furthermore, the UPC/Bar code information could beused as a pointer to Web sites on the Internet. This bar code could be astandard Universal Product Code (UPC) or could be a special bar codeformat intended for use only with the remote control.

In an exemplary implementation, a bar code reader module with a serialinterface, such as are available from Symbol Technologies Inc., can beattached through the general purpose serial I/O connection 108 and UARTport 330. This bar code reader module may be physically incorporatedinto the housing 13 of the remote control, or may be in the form of aself contained external module connected via a cable to the serial I/Ojack 61. When so equipped, the bar code reader can be used as analternative to the keyboard for entry of data into input fields in HTMLpages. By way of example, FIG. 29 illustrates an application in which aconsumer can obtain additional information regarding a product from theInternet, the remote control communicating with the Internet in a mannersimilar to that previously described in connection with FIGS. 14-15.

To request information in this manner, the user would initially requestan HTML page containing an input field 2910 into which a UPC code isentered, either via the keyboard or by scanning the product itself withthe bar code reader. Preferably keyboard entry is provided as a backupin the event the UPC bar code label on the product is damaged, obscured,unreachable, or the like. An “EXIT” button 2915 is also provided on thisand subsequent pages so that the user can return to the BrowserApplication start page or other designated beginning point at any time.After capture of the UPC code 2930 by scanning the product with the barcode reader, selecting the “SUBMIT” 2940 button causes the remotecontrol Browser Application to transmit the UPC code data back to theURL from which the initial HTML page originated. At the originatingsite, this data can be used to directly index into a database of productinformation or, alternatively, may be used to index into a table ofother URLs (corresponding to manufacturer Web pages, for example) totransfer the request to a specific site from which the appropriateinformation is available. In either event, the resulting response is thetransmission of a page of HTML formatted data back to the remote control10 to cause display of the desired product information 2960. This pageof information can itself contain link(s) to additional page(s) ofinformation as seen in this example where selecting “COOKING DIRECTIONS”2970 results in the display of a secondary page of information 2980,which in turn can contain a link 2990 to yet another page, and so on. Inthis manner all needed product information can be made available to aconsumer.

The bar code reader may also be used in many other Internet basedapplications implemented in a similar manner to that described above forexample, grocery shopping, on line warranty registration, product and/orprice comparisons, and the like. It may also be used as an alternativeinput means during the process of acquiring song lyrics or user manualinformation as described earlier, by swiping the UPC on the productpackaging in place of manually entering text or setup data.

For use in facilitating interaction with the Internet and/or other modesof communication both wireless and wired, the remote control 10 can beadapted to dock to a keyboard. A view of the remote control 10 used in alandscape mode is illustrated in FIG. 17. In this manner, the keyboard300 and the remote control 10 can communicate such that the remotecontrol 10 can be used for sending email, talking in Internet chatrooms, etc. Communications via a network Internet would occur in amanner similar to that described in connection with FIGS. 14-15.

While specific embodiments of the invention have been described indetail, it will be appreciated by those skilled in the art that variousmodifications and alternatives to those details could be developed inlight of the overall teachings of the disclosure. Accordingly, theparticular arrangement disclosed is meant to be illustrative only andnot limiting as to the scope of the invention which is to be given thefull breadth of the appended claims and any equivalents thereof.

What is claimed is:
 1. A computer-readable media having computer executable instructions for displaying information in a display, the instructions performing steps comprising: retrieving a mark-up language formatted page having an embedded mark-up language formatted page tag comprised of a data field containing information indicative of a command code to be transmitted upon activation of a hyperlink displayed on the display; displaying the mark-up language formatted page including the hyperlink in the display; and in response to the hyperlink being activated, using the information in the data field to transmit the command code to a consumer appliance; wherein the transmitted command code is a command to tune the consumer appliance to a television channel.
 2. The computer-readable media as recited in claim 1, wherein the information comprises data for use in generating the command code.
 3. The computer-readable media as recited in claim 1, wherein the information comprises a pointer to data for generating the command code.
 4. The computer-readable media as recited in claim 1, wherein the mark-up language page depicts a representation of a user interface of a remote control.
 5. The computer-readable media as recited in claim 1, wherein the mark-up language formatted page is representative of a media guide.
 6. The computer-readable media as recited in claim 1, where the information is used to transmit an infrared command code to the consumer appliance.
 7. The computer-readable media as recited in claim 6, wherein the first information comprises data for use in generating the infrared code.
 8. The computer-readable media as recited in claim 6, wherein the information comprises a pointer to data for generating the infrared code.
 9. The computer-readable media as recited in claim 6, wherein the mark-up language page depicts a representation of a user interface of a remote control.
 10. The computer-readable media as recited in claim 6, wherein the mark-up language formatted page is representative of a media guide. 